Systems and methods for network congestion management using radio access network congestion indicators

ABSTRACT

Systems and methods for managing communications network congestion are provided. In an embodiment, the system includes a radio access network (RAN) interface configured to receive RAN congestion indicators, a congestion correlator module configured to correlate RAN congestion indicators to service congestion indicators, a database comprising a set of congestion based policy rules, a policy controller module configured to apply the congestion-based policy rules to achieve a policy decision, and a policy enforcement control point interface configured to transmit network control instructions to enforce the policy decisions. In another embodiment of the invention, a method is provided for managing communications network congestion, that includes receiving one or more radio access network (RAN) congestion indicators, correlating the one or more RAN congestion indicators to one or more service congestion indicators, applying a congestion-based policy rule based on service congestion indicators to generate a policy decision, and implementing the policy decision.

This application claims the benefit of U.S. Provisional Application No.61/301,071, filed Feb. 3, 2010, which is incorporated herein in itsentirety.

FIELD OF THE INVENTION

The present invention relates generally to communications networks, moreparticularly, to network congestion management using radio accessnetwork congestion indicators.

BACKGROUND

Portable computing devices such as laptop computers, personal dataassistants (PDAs), smart phones and the like are in common usage, manyfeaturing data communications support, powerful processors, larger andmore colorful displays, and wireless networking and internet browsingcapabilities. These advances in mobile technology have resulted in adramatic increase in the volume of data communicated on wirelessnetworks. These advances, coupled with subscribers seeking expandedmobility, drive subscribers to install and run data-hungry applicationson their mobile devices. Data traffic is growing due to a combination ofincreasing market share of data-centric portable devices such as iPhone®and Blackberry® devices, lower wireless data subscription costs, higherwireless data throughput, and easier mobile access to data-intensiveapplications and rich content, such as, video. These trends are drivingever-increasing demands for wireless data communications.

Exacerbating the problem of managing this ever-increasing demand forwireless communications services is that a large percentage of wirelesstraffic within urban centers is managed by a small percentage of thecell sites. As a result, radio access network (RAN) congestion causesdegradation in the quality of service for mobile data customers. RANcongestion is a well known problem, however, the correlation of cellsite congestion to customers that are actively on those cell sites andtheir corresponding service plans is not. In particular, while networkoperators are employing intelligent probe-based solutions, such as thosefrom Kapsch CarrierCom and Netscout, to help understand the overallstatus of cell sites, including when and where congestion occurs, nomechanism exists to correlate this congestion information from RANprobes into intelligent policy decision and enforcement points in thecore wireless network.

What is therefore needed are systems and methods for network congestionmanagement using radio access network congestion indicators measured byRAN probes that are applied within intelligent policy controllers thatcan then regulate the network resources used by users to better manageservice quality.

SUMMARY OF THE INVENTION

Embodiments of the present invention provide systems and methods thatimprove network congestion management. In an embodiment, a system formanaging communications network congestion is provided that includes aradio access network (RAN) interface configured to receive RANcongestion indicators, a congestion correlator module configured tocorrelate RAN congestion indicators to service congestion indicators, adatabase comprising a set of congestion based policy rules, wherein thecongestion-based policy rules establish control responses based on atleast one or more service congestion indicators, a policy controllermodule configured to apply the congestion-based policy rules to achievea policy decision, and a policy enforcement control point interfaceconfigured to transmit network control instructions to enforce thepolicy decisions.

In another embodiment of the invention, a method is provided formanaging communications network congestion, that includes receiving oneor more radio access network (RAN) congestion indicators, correlatingthe one or more RAN congestion indicators to one or more servicecongestion indicators, applying a congestion-based policy rule based onthe one or more service congestion indicators to generate a policydecision, and implementing the policy decision.

Further embodiments, features, and advantages of the invention, as wellas the structure and operation of the various embodiments of theinvention are described in detail below with reference to accompanyingpresent drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated herein and form a partof the specification, illustrate the present invention and, togetherwith the description, further serve to explain the principles of theinvention and to enable a person skilled in the pertinent art to makeand use the invention.

FIG. 1 depicts an exemplary operating environment for using RANcongestion indicators to implement policy decisions, according toembodiments of the invention.

FIG. 2 depicts an exemplary system for managing communications networkcongestion, according to an embodiment of the invention.

FIG. 3 provides an exemplary method for managing communications networkcongestion, according to an embodiment of the invention.

FIG. 4 depicts an exemplary computer system on which methods and systemsherein may be implemented, according to embodiments of the presentinvention.

The present invention will now be described with reference to theaccompanying drawings. In the drawings, like reference numbers canindicate identical or functionally similar elements. Additionally, theleft-most digit(s) of a reference number may identify the drawing inwhich the reference number first appears.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 provides an exemplary operating environment 100 for managingcommunications network congestion, according to embodiments of theinvention. Operating environment 100 includes user equipment 110, radioaccess network (RAN) 120, network access gateway 130, packet network140, RAN probe 150, congestion module 160 and policy controller 170.Operating environment 100 provides a simplified diagram of acommunications network to illustrate the concepts of network congestionmanagement. As would be recognized by persons of skill in the art,embodiments of the present invention can be used in any type ofcommunications network (e.g., wireline, wireless, or hybrid networks).

User equipment 110 is any device that provides a user access to one ormore networks. User equipment 110 can include, but is not limited to, alaptop computer, a personal digital assistant (PDA), a wireless phone, asmart phone, or other wireless mobile devices.

Access network 120 is a communications network that couples userequipment 110 to a packet data network 140. Access network 120 may be athird generation partnership project (3GPP) access network, a non-3GPPaccess network, or other types of access networks. Exemplary 3GPP accessnetworks include the UMTS terrestrial radio access network (UTRAN) andthe GSM EDGE radio access network. Other access networks include, butare not limited to WiFi, WiMAX, CDMA2000, GSM, and LTE.

Network access gateway 130 provides an interface between access network120 and packet data network 140. In a 3GPP network, network accessgateway 130 may be the Gateway General Packet Radio Service (GPRS)Support Node (GGSN). Network access gateway 130 may also act as a policyenforcement point.

RAN probe 150 passively monitors RAN 120 to gather RAN congestionindicators. Example RAN probes are provided by Netscout and KapschCarriercom. RAN probe 150 is configured to passively gather, forexample, RAN congestion indicators such as dropped packets, droppedcalls, RAN power consumption, and RAN bit error rates. In a UMTS/UTRANnetwork, for example, the RAN probe would monitor RAN activity on theIub interface between the NodeB and the radio network controller (RNC).RAN probe 150 transmits congestion data records containing RANcongestion indicators to Congestion Module 160. In an embodiment,congestion data records are transmitted to Congestion Module 160 using aUDP protocol.

FIG. 2 depicts an exemplary system for managing communications networkcongestion, according to an embodiment of the invention. In particular,FIG. 2 highlights Congestion Module 160 and Policy Controller 170. Thespecific functions and characteristics of Congestion Module 160 andPolicy Controller 170 are associated within specific modules for ease ofexplanation, which is not intended to limit the scope of the inventionbased on the specific boundaries established by the block diagrams. Forexample, FIG. 2 illustrates a separate congestion module and policycontroller, these systems could be incorporated into a single system orreside separately in two systems as shown in FIG. 2.

Congestion Module 160 includes RAN Congestion Probe Interface 205,Congestion Correlator Module 210, Policy Controller Interface 215, RANCongestion State Module 220, RAN Congestion History Module 225, ServiceCongestion History Module 230, Subscriber Activity Module 235 andReporting Interface 240.

RAN Congestion Probe Interface 205 interfaces with RAN Probe 150. RANCongestion Probe Interface 205 receives congestion data recordscontaining RAN congestion indicators from RAN Probe 150. RAN CongestionProbe Interface 205 also transmits control messages to RAN Probe 150. Inparticular, RAN Congestion Probe Interface 205 instructs RAN Probe 150as to what types of RAN congestion indicators should be transmitted andhow frequently such indicators should be captured and transmitted. RANCongestion Probe Interface 205 is coupled to Congestion CorrelatorModule 210.

In addition to being coupled to RAN Congestion Probe Interface 205,Congestion Correlator Module 210 is also coupled to RAN Congestion StateModule 220, RAN Congestion History Module 225, Service CongestionHistory Module 230, Subscriber Activity Module 235, Policy ControllerInterface 215 and Reporting Interface 240.

Congestion Correlator Module 210 provides a number of functions. Inparticular, in an embodiment Congestion Correlator Module 210 determineswhat type of RAN congestion indicators should be requested from Probe150 and how frequently the indicators should be sent. The frequency ofreceipt of RAN congestion indicators can be based on Probe 150 detectinga particular change in congestion indicators. For example, a bit errorrate exceeding a particular threshold could trigger the capture andtransmission of a set of congestion indicators. Alternatively,Congestion Correlator Module 210 can set the frequency for receipt ofcongestion indicators based on the congestion state for a RAN (e.g.,when in a congested state, receive more frequent congestion indicators),based on the time of day given historical congestion patterns (e.g.,when a particular time of day is known to experience congestion,receiving more frequent congestion indicators) or based on subscriberactivity within the radio access network (e.g., when there are manysubscribers connected through a particular radio access network,receiving more frequent congestion indicators.)

Upon receipt of RAN congestion indicators, Congestion Correlator Module210 correlates the RAN congestion indicators to service congestionindicators. A service congestion indicator identifies whether, forexample, IP bearer services are likely to be congested based on RANcongestion, and therefore service quality to users would likely beadversely affected. In an embodiment, service congestion indicators caninclude an indicator of present service congestion and an indicator ofpredicted service congestion in a future time period.

Congestion Correlator Module 210 generates service congestion indicatorsthrough a variety of approaches. In one embodiment, the servicecongestion indicator is simply a copy of the RAN congestion indicators.In another embodiment, Congestion Correlator Module 210 derives servicecongestion indicators based on RAN congestion state information and thereceived RAN congestion indicators. In another embodiment, CongestionCorrelator Module 210 derives service congestion indicators based on RANcongestion history information for a particular RAN and the received RANcongestion indicators. In another embodiment, Congestion CorrelatorModule 210 derives service congestion indicators based on subscriberactivity within a RAN and the received RAN congestion indicators.Alternatively, in another embodiment Congestion Correlator Module 210derives service congestion indicators based on the received RANcongestion indicators and a combination of one or more of RAN congestionstate information, RAN congestion history information, servicecongestion history, and subscriber activity within a RAN.

Upon generation of service congestion indicators, Congestion CorrelatorModule 210 provides the service congestion indicators to PolicyController Interface 215, which in turn provides the indicators topolicy controller 170 via Congestion Module Interface 245.

Additionally, in an embodiment, Congestion Correlator Module 210provides RAN congestion indicators and service congestion indicators toReporting Interface 240. Reporting Interface 240 transmits theseindicators to a reporting system.

RAN Congestion State Module 220 includes congestion state informationfor all RANs for which Congestion Module 160 is coupled. For example,Congestion Module 160 may be interfaced to one hundred RANs. RANCongestion State Module 220 would provide an indication of the currentcongestion state for each RAN.

RAN Congestion History Module 225 includes congestion state historicalinformation for all RANs for which Congestion Module 160 is coupled. Forexample, RAN Congestion History Module 225 may include congestion stateinformation for the last week for one hour increments that indicate thecongestion state of each RAN coupled to Congestion Module 160.

Service Congestion History Module 230 includes service congestionhistorical information with a correlation to RAN congestion historicalinformation. For example, Service Congestion History Module can includea measure of IP Bearer Service congestion and RAN congestion serviceindicators for the last week (or any duration) for one hour increments(or any increment). This data can be used to assist in predictingservice congestion based on RAN congestion.

Subscriber Activity Module 235 indicates the subscribers that areserviced by a RAN at a given time for each RAN coupled to CongestionModule 160.

Policy controller 170 includes Congestion Module Interface 245, PolicyController Module 250, Policy Enforcement Control Point 255, SubscriberData Interface 260, Congestion-Based Policy Rules 265 and MarketingSystem Interface 270.

Policy controller 170, at a high level, includes subscriber profiles andnetwork policies needed to manage network resources, such as bandwidth,according to a subscriber, session, and/or application. A serviceprovider may apply a policy based on business rules associated with avariety of factors (e.g., service tiers and/or dynamic parameters suchas time of day). The present invention focuses on business rules basedon congestion factors, however, as will be known by individuals skilledin the relevant arts, business rules implemented by policy controllersconsider many other factors in making policy decisions.

Upon receiving service congestion indicators, Policy Controller Module250 generates policy decisions by applying congestion-based policy rulesthat are stored in Congestion-Based Policy Rules depository 265. Asimple congestion-based policy rule, for example, is that if a servicecongestion indicator indicates service congestion is likely, then reducethe bandwidth permitted by all users that have standard usage plans,while allowing users with premium usage plans to continue to receivetheir full bandwidth allotment. A more complex congestion based policyrule may consider, for example, the service congestion indicator, thesubscriber usage habits, the subscriber service plans, the types ofservices being used by subscribers, and generate a policy decision ordecisions that impact different groups of subscribers based on thesefactors differently.

The congestion-based policy rules consider service congestion indicatorsrelative to the current congestion status and/or a predicted congestionstatus. In this way, different congestion rules can be implemented toeither reduce congestion or to avoid going into a congested state toensure a particular quality of service for premium customers. In anembodiment, the policy rules can also utilize RAN congestion stateinformation, RAN congestion history information, service congestionhistory and subscriber activity to generate policy decisions.

In order to use subscriber information in generating a policy decision,in an embodiment Policy controller 140 is coupled to a variety ofsubscriber databases through subscriber data interface 260. Subscriberdata interface 260 provides access to a set of subscriber databasesincluding a subscriber state database, a subscriber profile database anda subscriber usage database. The subscriber state database includesinformation that identifies and defines a subscriber's network session.Subscriber state information includes the subscriber identifier for thesession. In embodiments of the invention, subscriber identifiers may beone or more of a Mobile Subscriber ISDN Number (MSISDN), a MobileIdentification Number (MIN), a Private Identifier, information about thenetwork such as the IP address the subscriber is currently using andwhat network or networks to which the subscriber is currently connected,device information such as the device being used and the version of thesoftware, location and roaming information, and other unique stateinformation.

The subscriber profile database includes static information about thesubscriber. This information may include the service tier (e.g., gold,silver, bronze) assigned to the subscriber.

The subscriber usage database includes static and dynamic informationrelated to the subscriber's usage history. The subscriber's historyincludes, but is not limited to the subscriber's data usage history. Inembodiments of the present invention, subscriber usage database maystore information about the amount of data used on a per-applicationbasis by the subscriber's user equipment 110 in previous sessions.

When Policy Control Module 250 makes a policy decision, Policy ControlModule 250 provides control messages that implement the policy decisionto Policy Enforcement Control Point Interface 255. Policy EnforcementControl Point Interface 255 transmits the control messages to NetworkAccess Gateway 130. Network Access Gateway then enforces the policydecision, for example, by denying access of users to video streamingapplications that may be a source of service congestion.

FIG. 3 provides an exemplary method 300 for managing communicationsnetwork congestion, according to an embodiment of the invention. For thepurposes of illustrating method 300, reference is made to the exemplaryoperating environment depicted in FIG. 1 and the exemplaryimplementations of a congestion module and policy controller in FIG. 2.These references are intended only for ease of illustration, and notintended to limit the invention to the specific embodiments within FIGS.1 and 2.

Method 300 begins in step 310. In step 310 one or more RAN congestionindicators are received. For example, Congestion Module 160 receives acongestion data record from RAN Probe 150 that includes one or more RANcongestion indicators.

In step 320, the RAN congestion indicators are correlated to one or moreservice congestion indicators. For example, Congestion Correlator Module210 correlates the RAN congestion indicators to service congestionindicators. In an embodiment, the RAN congestion indicators can betransmitted directly to Policy Controller Module 250. In this scenario,congestion based policy rules would include policy rules that depend onRAN congestion indicators rather than service congestion indicators. Avariety of approaches are used to correlate RAN congestion indicators toservice congestion indicators.

In one embodiment, the service congestion indicator is simply a copy ofthe RAN congestion indicators. In another embodiment, CongestionCorrelator Module 210 derives service congestion indicators based on RANcongestion state information and the received RAN congestion indicators.In another embodiment, Congestion Correlator Module 210 derives servicecongestion indicators based on RAN congestion history information for aparticular RAN and the received RAN congestion indicators. In anotherembodiment, Congestion Correlator Module 210 derives service congestionindicators based on subscriber activity within a RAN and the receivedRAN congestion indicators. Alternatively, in another embodimentCongestion Correlator Module 210 derives service congestion indicatorsbased on the received RAN congestion indicators and a combination of oneor more of RAN congestion state information, RAN congestion historyinformation, service congestion history, and subscriber activity withina RAN.

In step 330 one or more congestion-based policy rules are applied basedon at least the service congestion indicator. For example, uponreceiving service congestion indicators, Policy Controller Module 250generates policy decisions by applying congestion-based policy rulesthat are stored in Congestion-Based Policy Rules depository 265. Asimple congestion-based policy rule, for example, is that if a servicecongestion indicator indicates service congestion is likely, then reducethe bandwidth permitted by all users that have standard usage plans,while allowing users with premium usage plans to continue to receivetheir full bandwidth allotment.

In step 340, the policy decision is implemented. For example, whenPolicy Control Module 250 makes a policy decision, Policy Control Module250 provides control messages that implement the policy decision toPolicy Enforcement Control Point Interface 255. Policy EnforcementControl Point Interface 255 transmits the control messages to NetworkAccess Gateway 130. Network Access Gateway then enforces the policydecision, for example, by denying access of users to video streamingapplications that may be a source of service congestion.

The following three examples illustrate how embodiments of the inventionare used to manage network congestion to affect customer serviceexperiences. In one example, it is a Monday afternoon and User A has anall-you-can-use data plan with her service provider. She is watchingvideos on YouTube. Because the network is not congested, she is allowedto burst for the period of time that she is watching the video. Thus,her service quality is quite good. On Monday evening, she returns to theYouTube service to show her friends the videos that she was watchingearlier. She is attached to cell site A, which is experiencingcongestion. A congestion module, such as Congestion Module 160, receivesupdated RAN congestion indicators from a probe, such as RAN probe 150. Apolicy controller module, such as Policy Controller Module 250 looks upthe cell site and the attached subscribers, along with theirentitlements and profiles. Policy Controller Module 250 applies acongestion-based policy rule, such that based on the RAN congestionindicator, all subscribers who are on an all-you-can use data plan havetheir QOS downgraded. This policy decision is then transmitted by apolicy enforcement control point interface to a network access gatewayto effect the policy decision. As a result, User A is downspeeded duringthe congestion event. In an embodiment, User A also receives a proactivenotification (e.g., an SMS message) from the service provider advisingthat her connection will be downspeeded according to her fair usagepolicy. The transmission of the SMS message is initiated throughMarketing System Interface 270 following the policy decision todownspeed service. The notification will offer her an opportunity toupgrade her service to the next service level or purchase a temporaryspeed boost. Alternatively, the policy decision could include theblocking of a service known to consume significant bandwidth, such as,for example streaming video access is blocked, or even more specificallystreaming video access from Youtube is blocked.

In another example, it is Monday evening and User B is currentlydownloading music from his apartment and is connected to Cell Site A.User B is a premium subscriber and is experiencing a slower than usualdownload. Cell Site A is currently experiencing high levels ofcongestion. A congestion module, such as Congestion Module 160, receivesan updated congestion indicator in real time from a RAN probe, such asRAN probe 150. As in the first example, Congestion Correlator Module 210correlates the RAN congestion indicator to a service congestionindicator and transmits the service congestion indicator to PolicyController Module 250. Policy Controller Module 250 determines whatsubscribers are attached to the cell site, along with their entitlementsand profiles. Policy Controller Module 250 makes a policy decision todowngrade the QoS for subscribers that have all-you-can use data plans,but not to downgrade QoS for subscribers that have premium plans. Thepolicy decision is implemented by transmitting control instructions fromPolicy Enforcement Control Point Interface 255 to the Network AccessGateway, for example, a GGSN. As a result User B, as a premiumsubscriber is not targeted for downgrade, and his service experienceimproves as congestion abates on a Cell Site A.

In a third example, rather than provide a reactive policy decision, aproactive policy decision is made. The present invention can predictservice congestion situations based on the RAN congestion indicators,RAN congestion history and service congestion history to prevent users,such as premium users, from experiencing congestion, or at leastreducing congestion for selected users. Congestion Correlator Module 210includes the capability to perform pattern recognition, such that when aseries of received RAN congestion indicators are mirroring a patternseen before within the RAN congestion history that corresponds to aservice congestion event in the Service Congestion History Module 230,then the Congestion Correlator Module 210 generates a predictive servicecongestion indicator that is transmitted to policy controller module255. Congestion-based rules are established that address how to addressinstances of predicted service congestion. For example, one rule mightsimply be to send an SMS message to all users within the effected cellsite that indicates network congestion is likely and encouraging them toreduce usage. Alternatively, certain subscriber classes can have theirQoS scaled down in moderation.

In an embodiment of the present invention, the methods and systems ofthe present invention described herein are implemented using well-knowncomputers, such as a computer 400 shown in FIG. 4. The computer 400 canbe any commercially available and well-known computer capable ofperforming the functions described herein, such as computers availablefrom International Business Machines, Apple, Sun, HP, Dell, etc.

Computer 400 includes one or more processors (also called centralprocessing units, or CPUs), such as processor 410. Processor 410 isconnected to communication bus 420. Computer 400 also includes a main orprimary memory 430, preferably random access memory (RAM). Primarymemory 430 has stored therein control logic (computer software), anddata.

Computer 400 may also include one or more secondary storage devices 440.Secondary storage devices 440 include, for example, hard disk drive 450and/or removable storage device or drive 460. Removable storage drive460 represents a floppy disk drive, a magnetic tape drive, a compactdisk drive, an optical storage device, tape backup, ZIP drive, JAZZdrive, etc.

Removable storage drive 460 interacts with removable storage unit 470.As will be appreciated, removable storage drive 460 includes a computerusable or readable storage medium having stored therein computersoftware (control logic) and/or data. Removable storage drive 460 readsfrom and/or writes to the removable storage unit 470 in a well-knownmanner.

Removable storage unit 470, also called a program storage device or acomputer program product, represents a floppy disk, magnetic tape,compact disk, optical storage disk, ZIP disk, JAZZ disk/tape, or anyother computer data storage device. Program storage devices or computerprogram products also include any device in which computer programs canbe stored, such as hard drives, ROM or memory cards, etc.

In an embodiment, the present invention is directed to computer programproducts or program storage devices having software that enablescomputer 400, or multiple computer 400 s to perforin any combination ofthe functions described herein

Computer programs (also called computer control logic) are stored inmain memory 430 and/or the secondary storage devices 440. Such computerprograms, when executed, direct computer 400 to perform the functions ofthe present invention as discussed herein. In particular, the computerprograms, when executed, enable processor 410 to perform the functionsof the present invention. Accordingly, such computer programs representcontrollers of the computer 400.

Computer 400 also includes input/output/display devices 480, such asmonitors, keyboards, pointing devices, etc.

Computer 400 further includes a communication or network interface 490.Network interface 490 enables computer 400 to communicate with remotedevices. For example, network interface 490 allows computer 400 tocommunicate over communication networks, such as LANs, WANs, theInternet, etc. Network interface 490 may interface with remote sites ornetworks via wired or wireless connections. Computer 400 receives dataand/or computer programs via network interface 490. Theelectrical/magnetic signals having contained therein data and/orcomputer programs received or transmitted by the computer 400 vianetwork interface 490 also represent computer program product(s).

The invention can work with software, hardware, and operating systemimplementations other than those described herein. Any software,hardware, and operating system implementations suitable for performingthe functions described herein can be used.

While various embodiments of the present invention have been describedabove, it should be understood that they have been presented by way ofexample only, and not limitation. It will be understood by those skilledin the relevant art(s) that various changes in form and details may bemade therein without departing from the spirit and scope of theinvention as defined in the appended claims. It should be understoodthat the invention is not limited to these examples. The invention isapplicable to any elements operating as described herein. Accordingly,the breadth and scope of the present invention should not be limited byany of the above-described exemplary embodiments, but should be definedonly in accordance with the following claims and their equivalents.

1. A system for managing communications network congestion, comprising:a radio access network (RAN) interface configured: to receive RANcongestion indicators of both a first type and a second type, transmit acontrol message indicating that the RAN congestion indicators of thesecond type are to be received in the future, and no more of the RANcongestion indicators of the first type are to be received in thefuture, and in response to the control message, receiving additional oneor more RAN congestion indicators of the second type captured accordingto the control message; a congestion correlator module configured tocorrelate the additional one or more RAN congestion indicators of thesecond type to service congestion indicators by copying the additionalone or more RAN congestion indicators of the second type to the servicecongestion indicators; a database comprising congestion based policyrules, wherein the congestion-based policy rules establish controlresponses based on at least one or more service congestion indicators; apolicy controller module configured to apply the congestion-based policyrules to achieve a policy decision; and a policy enforcement controlpoint interface configured to transmit network control instructions toenforce the policy decision.
 2. The system of claim 1, furthercomprising a RAN congestion history module configured to store the RANcongestion indicators associated with a RAN as a function of time. 3.The system of claim 1, further comprising a RAN congestion state moduleconfigured to store congestion state information for a RAN.
 4. Thesystem of claim 1, further comprising a marketing interface configuredto transmit a marketing congestion indicator, wherein the marketingcongestion indicator includes an indication that a user's experiencewill be adjusted based on network congestion considerations.
 5. Thesystem of claim 1, further comprising an interface configured to gatherRAN user activity information, wherein the RAN user activity informationidentifies the users being serviced by a RAN and the type of servicesbeing provided.
 6. The system of claim 1, wherein the congestioncorrelator module is further configured to analyze the RAN congestionindicators to generate service congestion indicators that predict futureservice congestion.
 7. The system of claim 1, wherein the congestioncorrelator module is further configured to generate service congestionindicators based on one or more of the RAN congestion indicators, RANcongestion states, RAN congestion trends, historical RAN congestionpatterns, and historical service congestion patterns.
 8. The system ofclaim 1, wherein the congestion-based policy rules adjust limitations onbandwidth allowances, adjust service traffic priority, or block accessto certain applications.
 9. The system of claim 1, wherein thecongestion-based policy rules are imposed against classes of users. 10.The system of claim 1, wherein the RAN congestion indicators includedropped packets, dropped calls, error rates, and RAN power consumption.11. The system of claim 1, wherein the communications network operatesusing a WIMAX, LTE, UMTS or CDMA protocol.
 12. The method of claim 1,wherein the control message further indicates a frequency for receipt ofthe RAN congestion indicators of the second type based on a congestionstate of the RAN.
 13. The method of claim 1, wherein the control messagefurther indicates a frequency for receipt of the RAN congestionindicators of the second type based on a time of day given historicalcongestion patterns.
 14. The method of claim 1, wherein the controlmessage further indicates a frequency for receipt of the RAN congestionindicators of the second type based on a subscriber activity within aRAN.
 15. A method for managing communications network congestion,comprising: receiving one or more radio access network (RAN) congestionindicators of a first type; receiving one or more radio access network(RAN) congestion indicators of a second type; transmitting a controlmessage indicating that the RAN congestion indicators of the second typeare to be received in the future, and no more of the RAN congestionindicators of the first type are to be received in the future; inresponse to the control message, receiving additional one or more RANcongestion indicators of the second type captured according to thecontrol message; correlating the additional one or more RAN congestionindicators of the second type to one or more service congestionindicators, wherein correlating the additional one or more RANcongestion indicators of the second type to the one or more servicecongestion indicators includes copying the additional one or more RANcongestion indicators of the second type to the one or more servicecongestion indicators; applying a congestion-based policy rule based onthe one or more service congestion indicators to generate a policydecision; and implementing the policy decision.
 16. The method of claim15, further comprising transmitting a reporting message that includesone or more of the RAN congestion indicators.
 17. The method of claim15, further comprising transmitting a marketing message that includes anindication that a congestion-based policy decision has been made. 18.The method of claim 17, further comprising transmitting a marketingoffer to one or more users that are impacted by the congestion-basedpolicy decision.
 19. The method of claim 15, further comprising storingone or more of the RAN congestion indicators and associating the one ormore of the RAN congestion indicators with a RAN.
 20. The method ofclaim 15, further comprising storing congestion state information basedon the RAN congestion indicators for a RAN.
 21. The method of claim 20,wherein the stored congestion state information includes a periodic andincremental logging of the RAN congestion indicators for the RAN. 22.The method of claim 15, wherein correlating the additional one or moreRAN congestion indicators of the second type results in the one or moreservice congestion indicators being the same as the additional one ormore RAN congestion indicators of the second type.
 23. The method ofclaim 15, wherein correlating the additional one or more RAN congestionindicators of the second type to the one or more service congestionindicators includes determining one or more service congestionindicators based on the additional one or more RAN congestion indicatorsof the second type and RAN state information.
 24. The method of claim15, wherein correlating the additional one or more RAN congestionindicators of the second type to one or more service congestionindicators includes determining one or more service congestionindicators based on the additional one or more RAN congestion indicatorsof the second type, and one or more of RAN congestion state information,historical service congestion associated with a RAN, subscriber activityassociated with the RAN, and time of day.
 25. The method of claim 15,wherein implementing the policy decision includes transmitting a secondcontrol message to a policy control enforcement point that adjusts theservice characteristics of users associated with a RAN for which theadditional one or more RAN congestion indicators of the second type arereceived.
 26. The method of claim 15, wherein the one or more servicecongestion indicators include a present state service congestionindicator, and a predicted state service congestion indicator.
 27. Themethod of claim 15, wherein the RAN congestion indicators includedropped packets, dropped calls, error rates and RAN power consumption.28. The method of claim 15, wherein the communications network operatesusing a WIMAX, LTE, UMTS or CDMA protocol.